home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
System Booster
/
System Booster.iso
/
Archives
/
ForCLI
/
0Utils13.lha
/
0Utils
/
.Conventions
< prev
next >
Wrap
Text File
|
1995-04-07
|
2KB
|
70 lines
This is a short list of conventions used when
creating the c-source templates "gen.c.tplt"
and ".c.Template"
1) Each of the Programs in this archive supports
"C:Version".
* This feature is in fact not to be notable,
but due to the fact many of the currently
found programs still do not support it, it
seemed to be notable. >8)
2) Each of the Programs in this archive supports
the string "$ARG: " in front of the argument
template, so other programs can ask for
the template w/out invoking the program.
to save some bytes or to support another
string, the define FORMATPREFIX (def =
"\0$ARG: ") can be redefined at compiletime.
* Should this header be replaced by ".Key "
for scripting compability?
* I personally would like to see this becoming
a standard - so a GUI might ask the user
for input (instead of the prompt).
3) Each of the Programs in this archive supports
an additional Flag "/W", if a "/M" Argument
does allow Patternmatching ( this are in fact
currently only the FILE/M[/W] arguments for
the 0Filters archive, if they are compiled with
"DEFINE PATTERNMATCHING"). Since this additional
flag _might_ cause problems with other versions
of dos.library, it can be switched off at compile
time by redefining WILDCARDFLAG (default = "/W")
* I personally would like to see this flag
being supported by the OS for the above
purpose. (if I rewrite dos.library,
I'll add it =8-))
4) For all Commands the full source is provided.
* I thought this would be normal for freeware
programs, but in he recent past, I noticed,
that many - most - of the released programs do
_not_ include source code. That is imho not
a very good decision, since nobody can say,
if the current programs can be run on os4
(if it comes) w/out recompilation. and if the
programmers are then still supporting their
products. 8-\
5) All 'filter' commands in the archive 0Filters
do accept multiple input files: "FILE/M"
if no input file is specified, STDIN is used.
else each of the defined files is used for input.
if the commands are compiled with the flag
PATTERNMATCHING, these inputfiles accept wildcards,
but the executables will grow about 120 Bytes.
6) All 'filter' commands in the archive 0Filters
do accept target redirection: "TO/K"
if no target file is specified, STDOUT is used
for output.